What is this?
The Sprinter Tool helps you plan sprints by automatically assigning Jira tickets to team members based on each person's role, availability, and capacity. Instead of manually spreading work across sprints in a spreadsheet, you upload two files and the tool does the math for you.
What you need
Two CSV files exported from your existing tools:
1
Team Roster CSV
A list of team members with their name, role (DEV, BA, QA, etc.), allocation %, and optionally their focus areas (e.g., Enhancements, M&O).
2
Jira Backlog CSV
An export from Jira containing tickets with their key, summary, estimate, status, priority, severity, sprint/workstream, and issue type.
How to use it
1
Upload files
Select your Team Roster and Jira Backlog CSVs. The tool auto-detects column names.
2
Adjust settings
Set the number of sprints, sprint length (weeks), and view mode. Optionally check field mappings.
3
Click "Process & Plan"
The tool assigns tickets to people across sprints based on capacity and priority.
4
Review results
See the Gantt timeline, open the Assignments Table for details, and check the Backlog for overflow.
What the tool does behind the scenes
It converts Jira time estimates (seconds) into hours, then auto-generates BA and QA effort from the DEV estimate. Tickets are assigned in priority order (highest severity/priority first) in three phases — DEV first, then BA, then QA — and each person's sprint capacity is never exceeded.
Tickets that don't fit within anyone's available capacity are placed in the Unassigned Backlog so nothing gets lost.
Tips
Field Mapping: If columns aren't detected correctly, click "Show Field Mapping" to manually match your CSV columns to the expected fields.
Filters & Export: Use the "Open Tools" button above the Gantt chart to filter by workstream, person, or sprint — and to download assignments as a CSV.
Assignments Table: For a full searchable and filterable view of every assignment, open the Assignments Table from the Tools drawer.